IMPROVEMENTS VERSION 1.00 --> 1.50:
-----------------------------------
- Original Registry values are no longer programmed "hard"
  into the program. They are now read from an external
  file and can also be stored into one. After selection
  or creation of this file, it remains stored as standard
  and does not have to be selected again for the next use.

- Therefore: Support for all currently available driver
  versions and presumably also for upcoming versions (if
  this structure is preserved). Some earlier driver
  versions had different data values, but all the same
  structure in the Registry.

- Therefore: Support for Voodoo3 cards. These do also have
  the same structure in the Registry, but partitially
  different data values.

- Therefore: After installation of another driver version,
  the program can pick the original Registry data of this
  driver use it as a base for modifications from there on.

- Extended and changed help and descriptions.

- Several smaller (non-critical) bugs / spelling mistakes
  have been fixed.



FUNCTIONING / EXPLANATION:
--------------------------

Under Windows 2000 several versions of Voodoo4/5 drivers
create the effect that the display refresh rate remains at
60Hz under OpenGL/Glide and sometimes under Direct3D, even
if set to a higher value in DXDIAG or the respective
application / game.

This program merely changes the available frequencies
(stored in the registry) so that the frequencies
considered to be to low no longer remain available, and
the driver is forced to choose a higher frequency (the
one assigned here).

The program proceeds as follows: It restores (not before
applying changes) the original values of the Registry path
shown below by using the values from the appropriate file
(this is why it should be created before any changes to
these settings!). Afterwards, it deletes all the
frequencies under the respective resolution that are lower
than the selected one.

Under the Registry path

"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
3dfxvs\Device0\TIMINGS"

the different possible resolutions of the card are stored
(as subkeys). Under each resolution, the different
available frequencies are stored as further subkeys.
By deleting such a key, the frequency under that
resolution is no longer available. The driver tries to use
the next higher frequency, if this is possible according
to the monitor setting (driver or PnP data). If not, the
whole resolution will no longer remain available (even
for the Windows desktop!).

Thus you can increase the frequency for one or more
resolution with direct deletion for Windows, Glide, OpenGL
and Direct3D.

The Registry paths
"...Services\3dfxvs\Device1"
"...Services\3dfxvs\Device2"
"...Services\3dfxvs\Device3"
may also exist (depending on the card), possibly with each
containing a TIMINGS subkey, but the trick works without
modification of the values stored under these keys.
